See how a minor change to your commit message style can make a difference.
git commit -m"<type>(<optional scope>): <description>" \ -m"<optional body>" \ -m"<optional footer>"
See how a minor change to your commit message style can make a difference.
git commit -m"<type>(<optional scope>): <description>" \ -m"<optional body>" \ -m"<optional footer>"
| name | commit |
|---|---|
| description | Create a git commit using Conventional Commits style. Stages changes, analyzes diffs, and generates a well-formatted commit message with the appropriate type prefix and optional scope. |
Create a git commit following the Conventional Commits specification.
The Linux support thread in the GAMMA Discord (invite) is a great resource overall. It has videos and up to date resources along with knowledgeable folks to help you. The below works, is short, sweet and sufficient but you may want to go there nevertheless and see what the current state of the GAMMA on Linux art is.
Mord3rca's neat gamma-launcher tool makes it possible to install STALKER GAMMA natively on Linux bypassing GAMMA's installer which needs Windows to run.
This doc is a short summary of 2 other documents but aimed at using Steam instead of Lutris to run the game.
Before we look at some common commands, I just want to note a few keyboard commands that are very helpful:
Up Arrow: Will show your last commandDown Arrow: Will show your next commandTab: Will auto-complete your commandCtrl + L: Will clear the screenA pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
Reconstructed from Danny Postma's talk How I Built My Own AgentOS on Claude's Agent SDK (So You Can Too) (2026). This document is both a product spec for a human and an implementation prompt for an AI coding agent. Build exactly this system. Do not invent features that are not specified here.
Role contracts and prompts in this file are reconstructed from the talk, not his verbatim files. Mark every reconstructed prompt in code comments and docs as such.
There is no problem with being a noobie and I do not use the term to sligtht or disparage anyone.
This is a way to setup your permissions for running Plex in Linux. Different folks may use different methods.
The permissions concepts provided here apply to OSX, but the users and groups are controlled and modified differently, so much of this will not work properly. I think the command is dscl, but that could be out of date.
There are many ways to setup your permissions scheme in Linux, this methodology describes a way to do it, not everyone will like it, but it works for me, so whatever.